pp108 : Transactional and Non-transactional Web Service

Transactional and Non-transactional Web Service
This topic describes the Transactional and Non-transactional Web services used in MDM.


MDM is capable of consuming 2 types of Web services; the default Web services generated over database metadata, and any external Web service that you can import into Process Platform.

Transactional Web service


The Web service that confirms to the Process Platform protocol is classified as Transactional Web service. Each data object in Transactional Web service represents an object that can be used for transactions such as creating, editing, and synchronizing with the back-end.

The following sample illustrates the transactional Web service protocol in Process Platform:

<tuple>
    <old>
        <Employees>
            <EmployeeID>1</EmployeeID>
        </Employees>
    </old>
</tuple>


In case of Transactional Web service, each data object (such as 'Employees' in the above sample) is wrapped in a<tuple>protocol, which is a Process Platform standard, and contains the state of the transactional object. The following are some transaction formats used in Process Platform:

Format

Description

<tuple> <old>...</old> </tuple>

This format is used when Web service is retrieved from back-end.

<tuple> <new>...</new> </tuple>

This format is used when Web service is created in the client. If the format also carries thesync_idattribute, it denotes that the data is yet to be synchronized with the back-end.

<tuple> <old>...</old> <new>...</new> </tuple>

This format is used when Web service is updated in the server. If the format also carries thesync_idattribute, it denotes that the data is yet to be updated to the back-end.

 

Non-transactional Web service

The Web service that does not confirm to the Process Platform standard protocol is referred to as Non-transactional Web service. The Non-transactional Web service can be any of the following:

  • Web service from Java Call services
  • Web service generated over Business Process Model
  • Web service from an external Web service
  • Any custom Web service (such as XML Web service)

    The following sample illustrates non-transactional Web service: 
    <items>
    <item>
        <id/>
       ...
   </item>
    <item>
        <id/>
       ...
   </item>
</items>